-
Notifications
You must be signed in to change notification settings - Fork 11
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
UI lib updates 1 #178
UI lib updates 1 #178
Conversation
Passes sanity check. will run all pages and will run sample process. |
Branch definitely is working but its the testing that I'm currently troubleshooting. |
"WARNING: Unable to find an exact match for CDP version 117, so returning the closest version found: 115" |
selinum v4.13.0 - is the first compatible with 117 |
Running a test branch. Looks like some of the xml files are not coming through as intended and some of the table data is not seen during a page search. |
Clearly displaying log correctly but now showing 'graphite' text for the LogsTestIT-runOutputTest. Need to better understand graphite to see how its working under the hood. Are we missing some log set or other needed element. |
No errors for the :"Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 48.321 s <<< FAILURE! - in jpl.cws.test.integration.ui.InitiatorsTestIT" going to need to step through to actually see what's happening. Looks fine on personal and server check. |
…e. Clean up before merge but commiting for test
…jection. need to have layered escapes
**note \@test to skip test |
Ok only 3 failures left: Have some "temp" prints that need cleaned up before can be merged. 1.) Graphite not found on page
java.lang.AssertionError: text 'Graphite' NOT FOUND on page This has something to do with graphite logging. not sure what yet. 2.) runStartInitiatorTest suspect its loosing object within a table INSTALLER: 2023-10-10T03:18:33,947 INFO [ main] ntegration.ui.InitiatorsTestIT( 172) - No stats for this process 3.) runResultsTest |
…here. Checking with logs & migrate plugin
For 1 I feel like the jQuery migration updated a function that is used to load/manipulate the data. I'm re-adding the migrate plugin and printing the console log to see if I can get any clues. |
…the XML failed to parse)
Update jQuery to 3.7.0
Update Bootstrap to 3.3.7
Update Ace Editor to v1.5.0