Known Fixes

JUnit Testing not working (Spring 2026)

There could be multiple causes for this, so there are a few fixes you can try.

  1. Revert the Test Runner back to version 0.44
    • Go to Extensions in VS Code
    • Search for ‘Test Runner for Java’
    • Click the down arrow next to Uninstall
    • Click ‘Install Specific Version’
    • Select 0.44.0
    • Then click ‘Restart Extensions’
  2. Change the junit import
    • If you used generate tests, it likely generated a different import, so you will need to change it.
    • change org.junit.jupiter.api.Test; to org.junit.Test;
  3. Make all tests public
    • You then need to change all the tests to be in the format Public void Testname(). When they were generated they likely were not generated with that public keyword.

If this doesn’t fix it, you can try a combination of the following:

  1. Control + Shift + P, then Clean Java Language Server Workspace
  2. Delete the entire .lib folder, and when you go into the testing pane and select ‘Enable Java Tests’, select Junit, not Junit Jupiter
  3. If the error you are getting is that assertEquals is ambiguious, you will need to change any integer values inside the test to be Integer.valueOf(number). The tests don’t seem to like type T.

Google Chrome will not open

We are not entirely sure what causes this problem, but recreating your google chrome config file seems to fix it. Run this in terminal and then you should be able to open chrome

mv ~/.config/google-chrome ~/.config/google-chrome.bak

SSH Rule Update Error

We have updated the rules around being able to SSH into any OCCS system, and you may encounter an error while trying to do it the first time. Here is the fix

ssh-keygen -R occs.cs.oberlin.edu && ssh user@occs.cs.oberlin.edu

where user is your CS username

Unable to Open Chrome

If you are getting an issue where you cannot open Google Chrome, head to the TERMINAL and please run:

rm -rf ~/.config/google-chrome/Singleton*

This removes stale cache data and you should be able to open Chrome.

gh auth Failing to Run

If gh auth is not working run:

rm -rf ~/.config/gh/hosts.yml

Then you can rerun gh auth and it should work.

Keyring Pop up

You get a pop up that mentions Keyring errors, open TERMINAL and run the following command:

rm -rf ~/.local/share/keyrings/login.keyring

This will remove the login keyring, and should stop causing the errors.

Unable to SSH to McNulty

If you get the error where you cannot SSH into McNulty in VS Code, please open TERMINAL and run the following commands:

cd .ssh
chmod 0600 config

Then retry. You may need to close and reopen VS Code for this to work.

Authentication pop ups

If you are constantly getting pop ups asking you to authenticate, enter oberlin@123 when it pops up.