| 21:23 | <jmdyck> | So if esmeta raises a bogus error, what do I do? |
| 21:27 | <bakkot> | add the containing clause to esmeta-ignore.json, and if that doesn't work, complain to Michael Ficarra |
| 21:29 | <jmdyck> | The funny thing is, as far as i can tell, the pr didn't do anything to cause the error. |
| 21:32 | <jmdyck> | So does the error message tell me the clause-identifier that would need to be added to esmeta-ignore? |
| 21:33 | <jmdyck> | because I don't know esmeta's naming convention |
| 21:40 | <jmdyck> | That's https://github.com/tc39/ecma262/actions/runs/3397117278/jobs/5648935776. |
| 21:42 | <jmdyck> | For https://github.com/tc39/ecma262/actions/runs/3397080497/jobs/5648856698, it's raising a Parse Error, which I'm guessing esmeta-ignore doesn't help with. But even if it does, again, I don't know how esmeta wants me to refer to the Function constructor. Just "Function" ? |
| 21:49 | <jmdyck> | Re the failure of https://github.com/tc39/ecma262/pull/2246, adding "ECMAScriptFunctionObject.Construct" to esmeta-ignore didn't make the error go away, so complaining to Michael Ficarra . |
| 21:52 | <jmdyck> | (It weird that the workflow-run report doesn't link back to the PR.) |