-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Try reenabling helix for components #18636
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
Conversation
@MattGal looks like our "--" might have broken the attachment in the work items for failing tests to the download, it always goes to an empty tab for me now :( I thought java JDK was already installed in the past, at least in the comments of https://github.com/dotnet/core-eng/issues/5302 I assumed it would already be on the path for the helix work items, but I'm seeing java not found (when trying to install things from npm/yarn)
|
@javiercn can you help me figure out how to get yarn working? Looks like its not a java on path issues since I manually downloaded and installed it, and yarn still fails to install selenium like so:
|
I'm a bit confused, isn't that exactly what the build is complaining about? If you do java -v in the context where the build is run, does it succeed? |
Oh i think I see the issue, the path isn't setup early enough |
@javiercn getting closer, where's this config file coming from for the selenium, need to change where its looking on helix
|
@pranavkm looks like https://github.com/dotnet/aspnetcore/pull/18676/files change is making this harder for components to run on helix since its now looking for a relative path, can we do something to make this look for that config file in the local directory (just copy it over as part of build or something?) |
@javiercn looks like the content root being generated at compile time is not going to work well on helix, can you look into a fix for this to work on helix, we control how the app is packaged and deployed so a relative path from the current directory should work I think? aspnetcore/src/Components/test/testassets/TestServer/Components.TestServer.csproj Line 28 in e72223e
The error at runtime is a directory not found:
|
I think so, you could key that of from |
Okay finally some progress, @javiercn can you see if you can make out what's actually failing now? I'm seeing some errors around launching the server it looks like |
It seems is null refing here? Not sure what can be causing it to fail there. |
@HaoK are the agents persistent or are they transient, in the sense they get re-imagined/rebooted per run. We could try and remove the process tracking logic. |
@javiercn yeah i don't think we need process tracking logic at all on the helix agents, they shouldn't be getting reused |
I suggest we disable it then |
Sounds good to me, can you just push onto this branch the removal of the process tracking stuff that you don't think we need? |
@HaoK Is there a Helix env variable I can key this off? |
Yeah just use
|
branch looks messed up with builds not triggering, doing a merge/force push here @javiercn , just a heads up in case you have changes locally |
d4f6d37
to
7b6d835
Compare
Progress I think, tests are still failing but not due to selenium, console output is here @javiercn : |
@HaoK I'm unsubscribing from this thread as it's a bit noisy, but if you need my input on anything just let me know directly please. |
@javiercn @pranavkm so it looks like installing yarn nukes npm, which then causes issues when selenium runs, any ideas how these two are supposedly to play together, what should the steps be on the helix side for things to be installed correctly? Right now I just tried using npm to install yarn, and then running yarn install, which looks like it works, but when the tests run selenium blows up because npm's cli gets nuked by yarn I think |
@HaoK, you should be able to switch the test runner to use |
@pranavkm so looks like both yarn and npm are missing from node_modules after yarn install, Any idea what nukes those? |
Replaced by #21280 |
No description provided.