Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flaky test #313

Open
Tracked by #176
lishaduck opened this issue Nov 12, 2024 · 7 comments
Open
Tracked by #176

Flaky test #313

lishaduck opened this issue Nov 12, 2024 · 7 comments

Comments

@lishaduck
Copy link
Contributor

lishaduck commented Nov 12, 2024

Moving this thread so I don't lose track of it: ↓

I've noticed this there's a test that's been flaking ("Running using other configuration (without errors)"):

-- UNEXPECTED ERROR ------------------------------------------------------------

I ran into an unexpected error. Please open an issue at the following link:
  https://github.com/jfmengels/node-elm-review/issues/new

Please include this error message and as much detail as you can provide. Running
with --debug might give additional information. If you can, please provide a
setup that makes it easy to reproduce the error. That will make it much easier
to fix the issue.

Below is the error that was encountered.
--------------------------------------------------------------------------------
<local-path>/test/project-with-errors/elm-stuff/generated-code/jfmengels/elm-review/cli/<version>/review-applications/bd2a2bb6c965dac5241ce8c4d0615d83.js:10328
    		$temp$offset = offset + 
    						                    

SyntaxError: Unexpected end of input

  at loadCompiledElmApp (<local-path>/lib/load-compiled-app.js:28:18)
  at initWithoutWorker (<local-path>/lib/app-wrapper.js:144:21)
  "
  at Object.test (test/review.test.js:37:1)

Originally posted by @lishaduck in #308 (comment)

@lishaduck
Copy link
Contributor Author

I've noticed this there's a test that's been flaking ("Running using other configuration (without errors)"):

Yes, I've noticed the same thing. I had a look, thinking it could be us not waiting for the compilation to be finalized, but the code looks fine. I still think it's the writing of the file (or the loading of it, but that's weirder) that is getting cut off early somehow, but I haven't figured out how yet. 🤔

It sounds pretty recent though. I don't think we saw this one before, but I could be wrong.

Originally posted by @jfmengels in #308 (comment)

@lishaduck
Copy link
Contributor Author

lishaduck commented Nov 12, 2024

It sounds pretty recent though. I don't think we saw this one before, but I could be wrong.

Well, it's really started flaking. Will look into it.
For reference, here's the first failure from it: https://github.com/jfmengels/node-elm-review/actions/runs/11769034390/job/32779541170

EDIT: Commit-wise, there was a different flake on #306 (it's older than my work here, I think I remember seeing it a while ago), and then fs-extra (#303) seems to have started this flake.

EDIT 2: Am gonna try to see if I reproduce it before #303.

Originally posted by @lishaduck in #308 (comment)

@lishaduck
Copy link
Contributor Author

Was able to repro with 38453c1, so sadly not #303.

Originally posted by @lishaduck in #308 (comment)

@lishaduck
Copy link
Contributor Author

Huh. I can't repro on #304 for the life of me,1 so I guess it's gotta be #306 (or, I suppose, #305), which makes no sense.

Originally posted by @lishaduck in #308 (comment)

Footnotes

  1. I've run tests 10+ 9 times on the commit, to no avail.

@lishaduck
Copy link
Contributor Author

@jfmengels, any ideas?

Originally posted by @lishaduck in #308 (comment)

@lishaduck lishaduck mentioned this issue Nov 12, 2024
11 tasks
@lishaduck lishaduck changed the title Flakey test Flaky test Nov 12, 2024
@jfmengels
Copy link
Owner

jfmengels commented Nov 12, 2024

I haven't had the time to delve into it more, so my thoughts are still the same as what is written above.

Do you have the power to re-run CI runs by the way or is it only me? (Because if you can, then this is annoying but more easily bypassable).

@lishaduck
Copy link
Contributor Author

Do you have the power to re-run CI runs by the way or is it only me? (Because if you can, then this is annoying but more easily bypassable).

No, I don't unfortunately (surprisingly, GitHub has a single secure default for actions 🎉 🤣).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants